Skip to content

Conversation

@AlexanderShenshin
Copy link
Contributor

Description:

  • Updated release workflow to support NPM trusted publishing
    • Added id-token permissions
    • Added a step to bump NPM version to 11+
    • Removed NPM token usage

Related issue(s):

Fixes #26

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

@AlexanderShenshin AlexanderShenshin self-assigned this Oct 4, 2025
@changeset-bot
Copy link

changeset-bot bot commented Oct 4, 2025

⚠️ No Changeset found

Latest commit: 239935d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Oct 4, 2025

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 99.03% 2443/2467
🟢 Branches 92.53% 743/803
🟢 Functions 99.34% 454/457
🟢 Lines 99.08% 2382/2404

Test suite run success

1215 tests passing in 96 suites.

Report generated by 🧪jest coverage report action from 239935d

@AlexanderShenshin
Copy link
Contributor Author

Hi @jwagantall, could you please take a look at this PR when you have time?

Are these changes sufficient to use trusted NPM publishing or we have other TODOs for repo/package/workflows?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migrate NPM releases to Trusted Publishing

2 participants